System and Method for Communications Device and Network Component Operation

ABSTRACT

A system and method for communications device and network component operation in an ID/Locator Split Based heterogeneous network is provided. A method for control node operation includes receiving an attach request, and attempting to authenticate/authorize the communications node. The attach request is a request from a communications node to attach to a heterogeneous network. The method also includes if the communications node authenticated/authorized successfully, causing an identification and a location to be assigned for the communications node, completing an attachment for the communications node, and transmitting information to the communications node. The method further includes if the communications node did not authenticate/authorize successfully, sending an attach reject message to the communications node. The identification and the location are separate values.

This application claims the benefit of U.S. Provisional Application No.61/222,967, filed on Jul. 3, 2009, entitled “System and Method forCommunications Device and Network Component Operation,” whichapplication is hereby incorporated herein by reference.

TECHNICAL FIELD

The present invention relates generally to communications, and moreparticularly to a system and method for communications device andnetwork component operation in an ID/Locator Split Based heterogeneousnetwork.

BACKGROUND

With the further evolution of fixed-mobile broadband networks beyond3G/4G, there is a great need to further flatten the future broadbandnetwork architecture to improve network efficiency and performance,reduce network capital expenditure and operational expenditure, enablenew advanced features and services. Identity (ID) and locator (LOC)split is one of the key technologies that enables an ultra flat networkarchitecture and better support of mobility, security and multi-homingin that network environment.

In many previous and current generation networks, a communicationdevice's ID and location may usually be tied to the communicationdevice's address, for example, an Internet Protocol (IP) address. IPaddress describes the topological location of the host and is also usedfor identifying the host, which is very inefficient especially whenmobility is involved. When tied to an IP address, the communicationdevice's ID and location are typically bound together and if thecommunication device's location were to change, such as, when thecommunication device were to roam onto a different network (a visitednetwork), then the communication device's ID would also change.

With ID-locator split, a communication device's ID and location may nolonger be tied together. Then, when a communication device's locationchanges, it may not be necessary to change the communication device'sID. This may simplify network operation, thereby potentially reducingnetwork capital expenditure and operational expenditure since hardwareand software support requirements may be reduced.

SUMMARY OF THE INVENTION

These technical advantages are generally achieved, by embodiments of asystem and method for communications device and network componentoperation in an ID/Locator Split Based heterogeneous network.

In accordance with an embodiment, a method for control node operation isprovided. The method includes receiving an attach request, andattempting to authenticate/authorize the communications node. The attachrequest is a request from a communications node to attach to aheterogeneous network. The method also includes if the communicationsnode authenticated/authorized successfully, causing an identificationand a location to be assigned for the communications node, completing anattachment for the communications node, and transmitting information tothe communications node. The identification and the location areseparate values. The method further includes if the communications nodedid not authenticate/authorize successfully, sending an attach rejectmessage to the communications node.

In accordance with another embodiment, a method for communications nodeoperation is provided. The method includes transmitting an attachrequest, and receiving a response responsive to the attach request. Theattach request includes a request to attach to a heterogeneous network.The method also includes if the response indicates that the attachrequest was accepted, completing an attachment to the heterogeneousnetwork, and sending information over a communications link. Theresponse includes an identification and a location for thecommunications node, and the identification and the location areseparate values. The method further includes if the response indicatesthat the attach request was not accepted, transmitting a further attachrequest.

In accordance with another embodiment, a method for control nodeoperation is provided. The method includes receiving a locator updaterequest, and attempting to authenticate/authorize the communicationsnode. The locator update request is a request from a communications nodeoperating in a heterogeneous network. The method also includes if thecommunications node authenticated/authorized successfully, causing abinding to be computed for the communications node, updating the bindingfor the communication node, and completing a location update. Thebinding includes an identification and a location, and wherein theidentification and the location are separate values. The method furtherincludes if the communications node did not authenticate/authorizesuccessfully, sending a locator update reject message to thecommunications node.

An advantage of an embodiment is that a network handshake with split IDand locator information is provided for a UE, which allows for thelocation of the UE to change while allowing an ID of the host sessionfor the UE to remain constant.

A further advantage of an embodiment is that network attachment andlocation update with split ID and locator information resulting inimproved network efficiency and allowing for routing optimization, aswell as reduced network complexity are enabled. Furthermore, newfeatures and services not possible without split ID and locatorinformation are made possible.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the embodiments that follow may be better understood.Additional features and advantages of the embodiments will be describedhereinafter which form the subject of the claims of the invention. Itshould be appreciated by those skilled in the art that the conceptionand specific embodiments disclosed may be readily utilized as a basisfor modifying or designing other structures or processes for carryingout the same purposes of the present invention. It should also berealized by those skilled in the art that such equivalent constructionsdo not depart from the spirit and scope of the invention as set forth inthe appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the embodiments, and the advantagesthereof, reference is now made to the following descriptions taken inconjunction with the accompanying drawings, in which:

FIG. 1 a is a diagram of a heterogeneous network;

FIG. 1 b is a diagram of a control node;

FIG. 2 is a diagram of a message exchange in an attach procedure;

FIG. 3 is a diagram of a message exchange in a locator update procedure,wherein a UE/host updates its location without a gateway change;

FIG. 4 is a diagram of a message exchange in a locator update procedure,wherein a UE/host updates its location with a gateway change;

FIG. 5 a is a flow diagram of UE operations in an attach procedure;

FIG. 5 b is a flow diagram of CN operations in an attach procedure;

FIG. 6 a is a flow diagram of UE operations in a locator updateprocedure; and

FIG. 6 b is a flow diagram of CN operations in a locator updateprocedure.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The making and using of the embodiments are discussed in detail below.It should be appreciated, however, that the present invention providesmany applicable inventive concepts that can be embodied in a widevariety of specific contexts. The specific embodiments discussed aremerely illustrative of specific ways to make and use the invention, anddo not limit the scope of the invention.

The embodiments will be described in a specific context, namely aheterogeneous communications network with Third Generation PartnershipProject (3GPP), WiMAX, 3GPP2, wireless LAN (WLAN), and so on, wirelessaccess technologies. The invention may also be applied, however, toother wireless access technologies and wireless access technologycombinations, such as, CDMA, CDMA2000, HRPD, DSL, cable, xPON, GSM,GPRS, EDGE, UMTS, HSPA, EV-DO, LTE, LTE-A, WiFi, IEEE 802.11, and soforth.

FIG. 1 a illustrates a heterogeneous network 100. Heterogeneous network100 may have an ultra flat fixed-mobile converged broadband networkarchitecture and may feature the ID-locator split. Heterogeneous network100 includes two layers of networks: an access network 105 and a core orcontrol network 110.

Access network 105 consists of any number of possible access technologybased networks, ranging from fixed (DSL, Cable, WiFi, PON, etc.), mobile(GSM, CDMA, GPRS, EDGE, UMTS, HSPA/HSPA+, EV-DO, WiMAX, LTE, LTE+, etc.)and any other possible future new access technology based networks.Access network 105 also includes any type of access networkenvironments, either home network, or enterprise network, or wide areanetwork, or any possible types of future access network environments.Access network 105 permits user equipment (UE), such as UE 140, toconnect to core network 110 and access information, executeapplications, and so forth. UEs may also be commonly referred to ashosts, terminals, access terminals, mobile stations, subscribers,subscriber units, subscriber terminals, and so forth.

Core network 110 (also referred to as an ultra flat core network) isable to support aforementioned, any access technology based accessnetworks, and network environments (also known as heterogeneous networkenvironments). Key components in core network 110 are: Control Nodes(CN), such as CN 115, Gateways (GW), such as GW 120, Enhanced HomeSubscriber databases and Servers (HSS+), such as HSS+ 125, andApplication Servers (AS), such as AS 130.

In general, there may be several pieces of information associated with asingle UE/device/host session, including a host session identity (hostsession ID), a UE identity (UE ID), a charging record, and a locator.The host session ID may be used to uniquely identify a UE/device/hostsession, while a charging record may be associated with a usersubscription, which may use different UEs/devices/hosts and thereforemay be common to several different UE ID. For example, a single user maybe paying for several UEs under a single subscription. The locator maybe associated with a single UE/device/host.

CNs, such as CN 115, are a generalized control node that supportsID-locator split, network policy, device/user/host attach, detach,locator update, security, mobility control/support, tracking a bindingbetween a host session ID and a locator for a host session, and othersignaling/control related functions. CNs may store the bindinginformation of the host session ID and its locator (LOC), for example.

GWs, such as GW 120, are a generalized gateway function that supportsID-locator split, network policy enforcement, security, mobilitysupport, border router, and other bearer and interworking relatedfunctions. The GW may assign a locator as well as generate a chargingrecord for a host session.

HSS+, such as HSS+ 125, is an enhanced subscriber database to supportID-locator split in addition to its current HSS functions. HSS+ storesthe binding information of the UE ID of a user/device/host and a CNlocator serving the user/device/host, for example.

ASs, such as AS 130, also support ID-locator split in addition to theregular functions of the application server, such as hostingapplications for execution on communications devices.

FIG. 1 b illustrates a detailed view of a CN 175. As shown in FIG. 1 b,CN 175 may be an implementation of a CN, such as CN 115 of heterogeneousnetwork 100, and may have an ultra flat fixed-mobile converged broadbandnetwork architecture. CN 175 includes a processor 180 to performoperations and tasks as well as execute programs and procedures, and amemory 182 that may be used to store information, data, programs,procedures, and so forth. Memory 182 may store information such asbinding information, such as host session ID and locator information forusers/devices/hosts, for example.

CN 175 also includes a network policy unit 184 that may be used toimplement network operation/communication policies, an attach unit 186that may be used to perform operations to allow a user to attach to anaccess technology, and a detach unit 188 that may be used to performoperations to allow a user to detach from an access technology. Attachunit 186 and detach unit 188 may be used in conjunction to allow a userto detach from a first access technology while it attaches to a secondaccess technology.

CN 175 further includes a locator update unit 190 that may be used toupdate locator information for a user as it moves about andattaches/detaches from various access technologies, a security unit 192that may be used to implement security processes and procedures (toauthenticate users, for example), and a mobility unit 194 that may beused to control the mobility of users based on the users service level,security level, and so forth, for example.

CN 175 may also include a control unit 196 that may be used to implementsignaling and control related functions in general. CN 175 may alsoinclude a binding track unit 198 that may be used to maintain (i.e.,keep track of a binding between a host session ID and a locator for auser. Although shown as separate units outside of processor 180, one ormore of units 184 through 198 may be implemented in processor 180.

FIG. 2 illustrates a message exchange 200 in an attach procedure.Message exchange 200 illustrates messages exchanged between devices andnetwork components in a heterogeneous network, such as the ultra flatfixed-mobile converged broadband network shown in FIG. 1, as a UE/host205 attaches to the heterogeneous network.

As UE/host 205 powers up, it is in need of network access to obtain aLocator (a control node). UE/host 205 may send an attach request messageto a new AN 207 (Event #1 220). New AN 207 may pass the attach requestmessage to a new CN 209 (Event #2 222). New CN 209 may initiate anauthentication/authorization of UE/host 205 by exchanging messagesbetween UE/host 205 and a HSS+ 213 (Event #3 224). Events #1-#3 may beconsidered to be the authentication/authorization of UE/host 205.

After successful authentication/authorization of UE/host 205, new CN 209may send a create default bearer request to a new GW 211 (Event #4 226).The default bearer request may include Quality of Service (QoS) andpolicy specifications for UE/host 205. New GW 211 may send back a createdefault bearer response to new CN 209 (Event #5 228). The create defaultbearer response may include an assigned locator for UE/host 205 and acharging record for a user session. The assigned locator may be similarto an IP address in previous generation networks and the charging recordmay be used to charge UE/host 205 for services used.

When new CN 209 receives the create default bearer response from new GW211, new CN 209 may send a locator update request to HSS+ 213 (Event #6230). The locator update request may request that HSS+ 213 store bindinginformation for UE/host 205. HSS+ 213 may store binding information forUE/host 205, including host session ID (ID_(SESSION)) with a new CNlocator that serves UE/host 205 (LOC_(CN)) (Event #7 232). Aftersuccessfully storing the binding information for UE/host 205, HSS+ 213may send a locator update response to new CN 209 (Event #8 234) and newCN 209 stores the binding information of UE/host 205 (ID_(UE)) with thenewly assigned locator of UE/host 205 (LOC_(UE)) (Event #9 236). Events#4-#9 may be considered to be the identification and locating of UE/host205.

New CN 209 sends an attach accept message to new AN 207 (Event #10 238)and new AN 207 passes the attach accept message to UE/host 205 (Event#11 240). New CN 209 also sends an initial context set up request to newAN 207 (Event #12 242). The initial context set up request may be basedon the QoS and policy agreed to or assigned earlier by a network policyserver in new CN 209. An access bearer is set up between UE/host 205 andnew AN 207 (Event #13 244). UE/host 205 sends an attach complete messageto new AN 207 after the completion of the set up of the access bearer(Event #14 246) and new AN 207 sends an attach complete message to newCN 209 (Event #15 248). Events #10-#15 may be considered to be thecompletion of the attach procedure for UE/host 205.

With the completion of the attach procedure for UE/host 205 to theheterogeneous network, UE/host 205 may transmit an initial uplink mediapacket to new GW 211 (Event #16 250). In response to the transmission ofthe initial media packet, new CN 209 sends an update bearer request withaccess bearer ID and an AN address/locator to new GW 211 (Event #17252). New GW 211 may respond with an update bearer response to new CN209 (Event #18 254). New GW 211 may then send an initial downlink mediapacket to UE/host 205 (Event #19 256). Events #16-#19 may be consideredto be the creation of links between UE/host 205 and new GW 211.

FIG. 3 illustrates a message exchange 300 in a locator update procedure.Message exchange 300 illustrates messages exchanged between devices andnetwork components in a heterogeneous network, such as the ultra flatfixed-mobile converged broadband network shown in FIG. 1, as a UE/host305 updates its location without a GW change.

Message exchange 300 may begin with UE/host 305 sending a locator updatemessage to new AN 307 (Event #1 320). UE/host 305 may send the locatorupdate message as a result of its moving away from an old AN, forexample. New AN 307 may pass the locator update message to new CN 309(Event #2 322). New CN 309 may retrieve UE/host 305 information from oldCN 311 by sending a retrieve user information request to old CN 311(Event #3 324). Information that new CN 309 may retrieve from old CN 311may include QoS, security associations, applications, and so forth. OldCN 311 may respond with a retrieve user information acknowledgement,which may contain the requested information (Event #4 326). New CN 309may initiate an authentication/authorization of UE/host 305 byexchanging messages between UE/host 305 and HSS+ 315 (Event #5 328).Authentication/authorization of UE/host 305 may be optional depending onimplementation of the heterogeneous network. Events #1-#5 may beconsidered to be the authentication/authorization of UE/host 305.

New CN 309 may decide that there is no GW change required even thoughUE/host 305 has changed CNs (from old CN 311 to new CN 309). However,since the AN has been changed, UE/host 305 needs to get a new locatorfrom old GW 313. New CN 309 sends an update bearer request to old GW 313(Event #6 330). The update bearer request may contain QoS and policyspecifications for UE/host 305. Old GW 313 may send back an updatebearer response to new CN 309 with newly assigned locator for UE/host305 and a charging record for UE/host 305 (Event #7 332). The assignedlocator may be similar to an IP address in previous generation networksand the charging record may be used to charge UE/host 305 for servicesused. New CN 309 may store the binding information for UE/host 305,including host session ID (ID_(SESSION)) with the newly assigned locatorof UE/host 305 (LOC_(UENEW)) (Event #8 334). Events #6-#8 may beconsidered to be the obtaining of new binding information for UE/host305.

If the heterogeneous network is designed so that UE/host 305 can keepthe same locator previously assigned by old GW 313 with it as itswitches to new CN 309 then there may be no new locator to be assigned.In such a situation there may be no newly assigned locator in Event #7332 and in Event #8 334 new CN 309 may just store the bindinginformation of UE/host 305 and an old locator of UE/host 305.

New CN 309 may then send a locator update request to HSS+ 315 (Event #9336). The locator update request may result in HSS+ 315 storing theupdated binding information of UE/host 305, including its ID and newlyassigned locator. HSS+ 315 may send a cancel locator request to old CN311 (Event #10 338). The cancel locator request may be sent by HSS+ 315to old CN 311 to have old CN 311 remove binding information of UE/host305, including its ID and the old locator of UE/host 305, which may beassociated with old CN 311 and old AN of UE/host 305. Old CN 311 removesbinding information (for example, (ID_(UF)/LOC_(UFOLD))) of UE/host 305(Event #11 340) and sends a cancel locator acknowledgement back to HSS+315 after removing the binding information of UE/host 305 (Event #12342). HSS+ 315 may then store the updated binding information of UE/host305 (Event #13 344). HSS+ 315 may store the host session ID(ID_(SESSION)) and a new CN locator of new CN 309 serving UE/host 305(LOC_(CNNEW)). Events #9-#13 may be considered to be the updating ofbinding information for UE/host 305.

HSS+ 315 may also send a locator update response message to new CN 309(Event #14 346). New CN 309 sends a locator update accept message to newAN 307 (Event #15 348), which may be passed onto UE/host 305 (Event #16350). UE/host 305 sends a locator update complete message to new AN 307to complete the locator update (Event #17 352). Events #14-#17 may beconsidered to be the completing the location update for UE/host 305.

FIG. 4 illustrates a message exchange 400 in a locator update procedure.Message exchange 400 illustrates messages exchanged between devices andnetwork components in a heterogeneous network, such as the ultra flatfixed-mobile converged broadband network shown in FIG. 1, as a UE/host405 updates its location with a GW change.

Message exchange 400 may begin with UE/host 405 sending a locator updatemessage to new AN 407 (Event #1 420). UE/host 405 may send the locatorupdate message as a result of its moving away from an old AN, forexample. New AN 407 may pass the locator update message to new CN 409(Event #2 422). New CN 409 may retrieve UE/host 405 information from oldCN 411 by sending a retrieve user information request to old CN 411(Event #3 424). Information that new CN 409 may retrieve from old CN 411may include QoS, security associations, applications, and so forth. OldCN 411 may respond with a retrieve user information acknowledgement,which may contain the requested information (Event #4 426). New CN 409may initiate an authentication/authorization of UE/host 405 byexchanging messages between UE/host 405 and HSS+ 417 (Event #5 428).Authentication/authorization of UE/host 405 may be optional depending onimplementation of the heterogeneous network. Events #1-#5 may beconsidered to be the authentication/authorization of UE/host 405.

New CN 409 may decide that a GW change is required (from old GW 413 tonew GW 415) (Event #6 430). New CN 409 may send a create default bearerrequest to new GW 415 (Event #7 432). The create default bearer requestmay include QoS and policy specifications for UE/host 405. New GW 415may send back a create default bearer response to new CN 409 (Event #8434). The create default bearer response may include a newly assignedlocator for UE/host 405 and a charging record for UE/host 405. Theassigned locator may be similar to an IP address in previous generationnetworks and the charging record may be used to charge UE/host 405 forservices used. New CN 409 may then store binding information for UE/host405 (Event #9 436). The binding information may include a host sessionID for UE/host 405 (ID_(SESSION)) and the newly assigned locator(LOC_(UENEW)). Events #6-#9 may be considered to be the obtaining of newbinding information for UE/host 405.

New CN 409 may then send a locator update request to HSS+ 417 (Event #10438). The locator update request may result in HSS+ 417 storing theupdated binding information of UE/host 405, including its ID and the newlocator of new CN 409. HSS+ 417 may send a cancel locator request to oldCN 411 (Event #11 440). The cancel locator request may be sent by HSS+417 to old CN 411 to have old CN 411 remove binding information ofUE/host 405, including its ID and the old locator of UE/host 405, whichmay be associated with old CN 411 and old AN of UE/host 405. Old CN 411removes binding information (for example, (ID_(SESSION)/LOC_(UEOLD))) ofUE/host 405 (Event #12 442) and sends a cancel locator acknowledgementback to HSS+ 417 after removing the binding information of UE/host 405(Event #13 444). HSS+ 417 may then store the updated binding informationof UE/host 405 (Event #14 446). HSS+ 417 may store the host session ID(ID_(SESSION)) and a new CN locator of new CN 409 serving UE/host 405(LOC_(CNNEW)). Events #10-#14 may be considered to be the updatingbinding information for UE/host 405.

Old CN 411 may send a delete bearer request to old GW 413 (Event #15448) and old GW 413 may send a delete bearer acknowledgement to old CN411 after the old bearer has been released (Event #16 450). Events #15and #16 may be considered to be deleting the old bearer.

HSS+ 417 may also send a locator update response message to new CN 409(Event #17 452). New CN 409 sends a locator update accept message to newAN 407 (Event #18 454), which may be passed onto UE/host 405 (Event #19456). UE/host 405 sends a locator update message to new AN 407 tocomplete the locator update (Event #20 458). Events #17-#20 may beconsidered to be the completing the location update for UE/host 405.

FIG. 5 a illustrates a flow diagram of UE operations 500 in an attachprocedure. UE operations 500 may be indicative of operations takingplace in a UE, such as UE 205, as the UE participates in an attachprocedure to attach to a heterogeneous network, such as the ultra flatfixed-mobile converged broadband network shown in FIG. 1. UE operations500 occurs whenever the UE initially powers on in the heterogeneousnetwork or after the UE returns to a coverage area of the heterogeneousnetwork after having left the heterogeneous network for an extendedperiod of time.

UE operations 500 may begin with the UE, as it powers up, needingnetwork access to obtain a locator (a control node (CN)). The UE maysend an attach request message to an AN (block 505). The AN may, inturn, pass the request message to a CN. The CN may initiate anauthentication/authorization of the UE by exchanging messages with theUE and a HSS+ (block 510).

If the UE authenticates and is authorized service in the heterogeneousnetwork, then the attach request from the UE may be accepted. The UE mayreceive an attach acceptance message from the AN (block 515). The attachacceptance message may provide to the UE its identification (e.g., ahost session ID) and location (e.g., a locator) information. The UE maythen participate in a completion of the attach procedure (block 520).The completion of the attach procedure may involve the setting up of anaccess bearer between the UE and the AN. With the completion of theattach procedure, the UE may send information over a UL and/or receiveinformation over a DL (block 525). UE operations 500 may then terminate.

If the attach request from the UE was not accepted, through anauthentication/authorization failure, an error in transmission, or soforth, the UE may reattempt the attach request at a later time byretransmitting the attach request. The UE may wait a specified amount oftime prior to retransmitting the attach request or the UE may generate arandomly generated wait time and allow the generated amount of time toelapse prior to retransmitting the attach request.

FIG. 5 b illustrates a flow diagram of CN operations 550 in an attachprocedure. CN operations 550 may be indicative of operations takingplace in a CN, such as CN 209, as a UE, such as UE 205, initiates anattach procedure to attach to a heterogeneous network, such as the ultraflat fixed-mobile converged broadband network shown in FIG. 1. CNoperations 550 occurs whenever the CN receives an attach request messagefrom the UE.

CN operations 550 may begin with the CN receiving an attach requestmessage from an AN, which received the attach request message from theUE (block 555). After receiving the attach request message, the CN mayneed to authenticate/authorize the UE to ensure that UE is authentic andis authorized to access the heterogeneous network. The CN may exchangemessages with the UE and a HSS+ to authenticate/authorize the UE (block560).

The CN may then cause the assignment of a charging record and a locator(block 565) for the UE. The CN may accomplish the binding of theidentifier and the locator for the UE by transmitting a locator updaterequest to the HSS+ (block 570). A GW may assign a locator and generatea charging record for the UE as part of binding information that iscreated for the UE. The CN may then complete the attach procedure bytransmitting an attach acceptance message to the UE and sending aninitial context set up request to the AN (block 575). The initialcontext set up request may initiate the establishment of an accessbearer between the UE and the AN. The CN may then transmit informationto the UE or receive information from the UE (block 585) and CNoperations 550 may then terminate.

If the attach request was not accepted, for example, because the UE wasnot authorized and/or authenticated, then the CN may transmit an attachreject message to the UE to inform the UE that its attach request wasrejected.

FIG. 6 a illustrates a flow diagram of UE operations 600 in a locatorupdate procedure. UE operations 600 may be indicative of operationstaking place in a UE, such as UE 205, as the UE participates in locatorupdate procedure in a heterogeneous network, such as the ultra flatfixed-mobile converged broadband network shown in FIG. 1. UE operations600 occurs whenever the UE moves away from a coverage area of an old ANand into a coverage area of a new AN.

UE operations 600 may begin with the UE sending a locator update messageto a new AN (block 605). The UE may send the locator update message tothe new AN as a result of it moving away from a coverage area of an oldAN and into a coverage area of the new AN, for example. The new AN maypass the locator update message to a new CN, which mayauthenticate/authorize the UE by exchanging messages with the UE, an oldCN, a HSS+, and the new CN (block 610). For example, the new CN mayretrieve UE information from the old CN. UE information may include QoSrestrictions, security associations, applications, and so forth.Additionally, the new CN may authenticate and authorize the UE with theHSS+.

The locator update may occur with or without a GW change. If themobility of the UE results in a locator update without a GW change, onlychanges in an existing access bearer may be needed to comply withchanges in QoS, policy, and so forth. However, if a locator update witha GW change is required, then a new access bearer may need to beestablished with a new GW and an existing access bearer with an old GWmay need to be deleted.

If the UE is authorized and authenticated, the UE may then receive alocator update acceptance (block 615). The locator update acceptance mayinclude new binding information for the UE, which may include a new CNlocator. The UE may send a locator update complete message to the new ANto complete the locator update (block 620) and UE operations 600 maythen terminate.

If the locator update request from the UE was not accepted, through anauthentication/authorization failure, an error in transmission, or soforth, the UE may reattempt the locator update request at a later timeby retransmitting the locator update request. The UE may wait aspecified amount of time prior to retransmitting the locator updaterequest or the UE may generate a randomly generated wait time and allowthe generated amount of time to elapse prior to retransmitting thelocator update request.

FIG. 6 b illustrates a flow diagram of CN operations 650 in a locatorupdate procedure. CN operations 650 may be indicative of operationstaking place in a CN, such as CN 209, as a UE, such as UE 205, movesaway from a coverage area of an old AN and to a coverage area of a newAN in a heterogeneous network, such as the ultra flat fixed-mobileconverged broadband network shown in FIG. 1. CN operations 650 occurswhenever the CN receives a locator update request message from the UE.

CN operations 650 may begin with a new CN receiving a locator updatemessage from the UE, where the locator update message may be forwardedto the new CN from a new AN (block 655). The new CN may proceed toauthenticate/authorize the UE (block 660). Authenticating/authorizingthe UE may include retrieving UE information from an old CN of the UEand exchanging messages with the UE, the old CN, and a HSS+ toauthenticate/authorize the UE, for example.

The new CN may then cause a computing of new binding information for theUE (block 665). If the mobility of the UE has not resulted in a locatorupdate that requires a GW change, the new CN may cause the computing ofnew binding information for the UE by requesting that an existing accessbearer for the UE be updated based on any new QoS restrictions, policychanges, and so forth. However, if the mobility of the UE has resultedin a locator update that requires a GW change, then the new CN may causethe computing of new binding information for the UE by creating a newaccess bearer for the UE with a new GW and deleting an existing accessbearer at an old GW.

The updated access bearer or the newly created access bearer may have anew binding, which may be updated at the HSS+ (block 670). The newbinding may include a locator, which may be provided to the UE as thenew CN completes the location update (block 675) and CN operations 650may then terminate.

If the locator update request was not accepted, for example, because theUE was not authorized and/or authenticated, then the CN may transmitlocator update reject message to the UE to inform the UE that itslocator update request was rejected.

Although the embodiments and their advantages have been described indetail, it should be understood that various changes, substitutions andalterations can be made herein without departing from the spirit andscope of the invention as defined by the appended claims. Moreover, thescope of the present application is not intended to be limited to theparticular embodiments of the process, machine, manufacture, compositionof matter, means, methods and steps described in the specification. Asone of ordinary skill in the art will readily appreciate from thedisclosure of the present invention, processes, machines, manufacture,compositions of matter, means, methods, or steps, presently existing orlater to be developed, that perform substantially the same function orachieve substantially the same result as the corresponding embodimentsdescribed herein may be utilized according to the present invention.Accordingly, the appended claims are intended to include within theirscope such processes, machines, manufacture, compositions of matter,means, methods, or steps.

1. A method for control node operation, the method comprising: receivingan attach request, wherein the attach request is a request from acommunications node to attach to a heterogeneous network; attempting toauthenticate/authorize the communications node; if the communicationsnode authenticated/authorized successfully, causing an identificationand a location to be assigned for the communications node, wherein theidentification and the location are separate values, completing anattachment for the communications node, and transmitting information tothe communications node; and if the communications node did notauthenticate/authorize successfully, sending an attach reject message tothe communications node.
 2. The method of claim 1, wherein causing anidentification and a location to be assigned comprises: creating adefault bearer for the communications node, the default bearercomprising the location and the identification for the communicationsnode; and updating information related to the communications node. 3.The method of claim 2, wherein updating information comprises storingthe location and the identification at a subscriber database.
 4. Themethod of claim 2, wherein updating information further comprisesstoring the location and the identification at a control node.
 5. Themethod of claim 1, wherein completing an attachment comprises: settingup a context for the communications node; and setting up an accessbearer for the communications node.
 6. The method of claim 5, whereincompleting an attachment further comprises, establishing communicationslinks for the communications node.
 7. The method of claim 6, whereinestablishing communications links comprises: updating a bearer for thecommunications node in response to detecting a first uplink media packettransmitted by the communications node; and transmitting a firstdownlink media packet to the communications node after receiving aresponse from an updating of information related to the communicationsnode.
 8. The method of claim 1, wherein the identification comprises anidentity for the communications node.
 9. A method for communicationsnode operation, the method comprising: transmitting an attach request,wherein the attach request comprises a request to attach to aheterogeneous network; receiving a response responsive to the attachrequest; if the response indicates that the attach request was accepted,completing an attachment to the heterogeneous network, and sendinginformation over a communications link, wherein the response comprisesan identification and a location for the communications node, andwherein the identification and the location are separate values; and ifthe response indicates that the attach request was not accepted,transmitting a further attach request.
 10. The method of claim 9,further comprising participating in an authentication and authorization.11. The method of claim 9, wherein the in response to determining thatthe attach request was not accepted, waiting a period of time.
 12. Themethod of claim 9, wherein completing an attachment comprises:establishing an access bearer; and sending an attach complete message.13. The method of claim 9, wherein the identification and the locationfor the communications node are used in a binding for a default bearer.14. The method of claim 13, wherein the binding is stored at asubscriber database.
 15. The method of claim 9, wherein theidentification comprises an identity and a charging record for thecommunications node.
 16. A method for control node operation, the methodcomprising: receiving a locator update request, wherein the locatorupdate request is a request from a communications node operating in aheterogeneous network; attempting to authenticate/authorize thecommunications node; if the communications node authenticated/authorizedsuccessfully, causing a binding to be computed for the communicationsnode, wherein the binding comprises an identification and a location,and wherein the identification and the location are separate values,updating the binding for the communication node, and completing alocation update; and if the communications node did notauthenticate/authorize successfully, sending a locator update rejectmessage to the communications node.
 17. The method of claim 16, whereinthe communications node switches from an old control node to the controlnode, and wherein authenticating/authorizing the communications nodecomprises: retrieving an old binding for the communications node fromthe old control node; and authenticating/authorizing the communicationsnode with a subscriber database using the old binding information. 18.The method of claim 17, wherein causing a binding to be computedcomprises creating a default bearer for the communications node, thedefault bearer comprising the location and the identification for thecommunications node.
 19. The method of claim 16, wherein causing abinding to be computed comprises, updating an existing bearer for thecommunications node.
 20. The method of claim 19, wherein the updating anexisting bearer is based on changes in policy, quality of servicerestrictions, or both.
 21. The method of claim 16, wherein causing abinding to be computed comprises, storing the location and theidentification for the communications node at the control node.
 22. Themethod of claim 16, wherein updating the binding comprises storing thelocation and the identification for the communications node at asubscriber database.